fix: CodePreview
- show explicit false props
#985
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
If the setting
useBooleanShorthandSyntax
is not set tofalse
in the https://github.com/algolia/react-element-to-jsx-string/tree/master options object, it will remove for good any prop looking like thisprop={false}
, even tho the default is set totrue
within the component.This is a problem because it can misguide people when they look at the code snippet, if they copy it and paste it -> they should see the same results, which today is not the case, for example for https://www.flowbite-react.com/docs/components/datepicker#autohide.
Changes
visible={false}
)sortProps
since it defaults totrue
This issue currently affects the following components:
MDX source code
Before
After